Scenario-Based Software Architecture Modeling Using Message Sequence Charts
نویسندگان
چکیده
Modern approaches in software development propose the use of software architectures to help handle the complexity of large software system developments. An important technique to define, analyze, validate, and evaluate a software architecture is through the use of scenarios. A scenario is a brief description of a single interaction of a stakeholder with a system. Scenario modeling is a well-accepted practice among software architects. However, there is no agreement on how to model scenarios. Message Sequence Charts (MSC) is a graphical-textual notation used to specify scenarios. This notation is standardized by the International Communication Union (ITU) and has a well-defined semantics. In this paper we present an approach for describing architectural scenarios using MSC. The paper focuses in the features proposed by the MSC notation to describe complex behaviors and time constraints. In addition, a brief discussion on the advantages of using MSC to validate architectural scenarios is presented. This validation is performed using an executable interpretation of MSC.
منابع مشابه
Deriving Message Sequence Charts from Use Case Maps Scenario Specifications
A set of scenarios is a useful way to capture many aspects of the requirements of a system. Use Case Maps are a method for scenario capture which is good for describing multiple scenarios, including scenario interactions, for developing an architecture, and for analysing architectural alternatives. However once a component architecture is determined, Message Sequence Charts are better for devel...
متن کاملMESA: Support for Scenario-Based Design of Concurrent Systems
The latest ITU-T standard syntax of Message Sequence Charts (MSCs) 16] ooers several operators to compose MSCs in a hierarchical , iterating, and nondeterministic way. However, current tools operate on MSCs that describe nite, deterministic behavior. In this paper, we describe the architecture and the partial implementation of Mesa, an MSC-based tool that supports early phases of the software d...
متن کاملUML Sequence Diagram Tutorial
What is a UML sequence diagram? UML sequence diagrams are used to represent or model the flow of messages, events and actions between the objects or components of a system. Time is represented in the vertical direction showing the sequence of interactions of the header elements, which are displayed horizontally at the top of the diagram. Sequence Diagrams are used primarily to design, document ...
متن کاملSecure Requirements Elicitation Through Triggered Message Sequence Charts
This paper argues for performing information-flow-based security analysis in the first phase of the software development life cycle itself ie in the requirements elicitation phase. Message Sequence Charts (MSC)s have been widely accepted as a formal scenario-based visual notation for writing down requirements. In this paper, we discuss a method for checking if a TMSC (Triggered Message Sequence...
متن کاملInherent Causal Orderings of Partial Order Scenarios
Scenario based requirements specifications are the industry norm for defining communication protocols. Basic scenarios captured as UML sequence diagrams, Message Sequence Charts (MSCs) or Live Sequence Charts (LSC) have partial order semantics that characterize system traces by restricting the possible order of events within those traces. The semantic partial order of the scenario specification...
متن کامل